Secure mechanism to deliver mobile traffic management configuration upon stub activation on a mobile device of a global service discovery server

ABSTRACT

A network is provided that includes a mobile device and a configurable stub having a stub configuration embedded in the mobile device non-transitory memory. An operating server has an operating server processor and the operating server is configured to send Short Messaging Service (SMS) messages. A processor controlled global service discovery server is configured to receive the stub configuration and to inform the mobile device about the operating server.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of PCT Patent Application No.PCT/US14/42817 filed on Jun. 17, 2014, which claims priority to U.S.Provisional Patent Application No. 61/836,108 filed on Jun. 17, 2013,and U.S. Provisional Patent Application No. 61/883,922 filed on Sep. 27,2013, the contents of both of which are incorporated by referenceherein.

BACKGROUND

Mobile devices are used by many persons in many different countries andon many different carriers. Information such as the country of use andthe carrier is important for mobile device traffic management systems.

Activation of a mobile device should be secure, while providingsufficient identifying information to identify the carrier, location,and other relevant information that a network service provider may needin order to provide efficient network management. This information isnot ideally provided in an SMS body since SMS can be faked (spoofed).

Accordingly, there is a need for a technique that provides a secure wayto deliver configuration upon activation.

BRIEF SUMMARY

In one aspect the present invention takes the form of a system having amobile device with an embedded stub having a stub configuration. Thesystem further includes an operating server having traffic managementprotocols and which is configured to support the communications of themobile device subject to the traffic management protocols. In addition,a global service discovery server receives the stub configuration andinforms the mobile device about the operating server.

The stub can cause the mobile device to communicate with the globalservice discovery server when the mobile device initially boots up, whenthe mobile device resets; or when a SIM card is changed. If the mobiledevice is associated with a first carrier but the changed SIM card isassociated with a second carrier the global service discovery serveridentifies a host server of the second carrier and then the mobiledevice is updated to be associated with the second carrier. The globalservice discovery server may identify an operator and country of use.

Beneficially the global service discovery server may check to see if themobile device is registered. If so, the mobile device profile may beupdated or registered. The mobile device profile might include at leastone of an IMEI number, a device manufacturer, a carrier, and a countryof use.

The stub can be activated upon receipt of a Short Messaging Service(SMS) from the operating server, which can be identified by theoperating server. If so, the stub may request application software fromthe operating server. The operating server may send the mobile devicethe requested application software.

The stub itself may be embedded by an original equipment manufacturerwhile the global service discovery server might send the mobile device amobile country code (MCC), a mobile network code (MNC), and anInternational mobile station equipment identity (IMEI).

Beneficially, the global service discovery server stores a security keywhich is also stored by the operator server. Then, the global servicediscovery server can send the key to the mobile device, the mobiledevice can then send that key to the operator server, and the operatorserver may verify the validity of the key and if valid send the mobiledevice application software.

According to another aspect the present invention includes a mobiledevice having an embedded stub with a stub configuration, an operatingserver having traffic management protocols to support the communicationsof the mobile device, and a global service discovery server forreceiving the stub configuration and for informing the mobile deviceabout the operating server. The stub sends the global service discoveryserver a request to register to mobile device, the global servicediscovery server registers the mobile device, the operating server sendsan activation SMS to the mobile device, in response to the SMS the stubcauses the mobile device to request an operation configuration, and theoperating server sends the operation configuration to the mobile device.

Beneficially, the stub causes the mobile device to request applicationsoftware from the operating server and then the operating server sendsthe requested application software to the mobile device, which is theninstalled.

In practice the stub causes the mobile device to communicate with theglobal service discovery server when the mobile device initially bootsup; when the mobile device resets; or when a SIM card is changed. If themobile device is associated with a first carrier, but the changed SIMcard is associated with a second carrier, the global service discoveryserver identifies a host server of the second carrier and the mobiledevice is updated to be associated with the second carrier.

The global service discovery server might identify an operator andcountry of use or the operation configuration might include at least oneof an IMEI number, a device manufacturer, a carrier, and a country ofuse. The stub may be embedded by an original equipment manufacturer. Theoperating server may send the mobile device a mobile country code (MCC),a mobile network code (MNC), and an International mobile stationequipment identity (IMEI).

Preferably the global service discovery server stores a key, theoperator server stores that key, the global service discovery serversends that key to the mobile device, the mobile device sends that key tothe operator server, the operator server verifies the validity of thekey and if valid sends the mobile device application software

According to another aspect of the invention, the invention is a networkhaving a mobile device with a mobile device processor, mobile devicetransient memory, a SIM card, mobile device non-transitory memorystoring a mobile device profile, mobile device bi-directionalcommunication capabilities, a mobile device operating system embedded inthe mobile device non-transitory memory, and a configurable stub havinga stub configuration embedded in the mobile device non-transitorymemory. The network further includes an operating server having anoperating server processor, operating server non-transitory memory,operating server bi-directional communication capabilities, an operatingserver operating system stored in the operating server non-transitorymemory, wherein the operating server is configured to support trafficmanagement protocols that support the bi-directional communications ofthe mobile device subject, and wherein the operating server isconfigured to send Short Messaging Service (SMS) messages. That networkalso includes a processor controlled global service discovery serverthat is configured to receive the stub configuration and to inform themobile device about the operating server.

In practice the stub causes the mobile device to communicate with theglobal service discovery server when the mobile device initially bootsup, when the mobile device resets, or when the SIM card is changed. Whenthe mobile device is associated with a first carrier but the changed SIMcard is associated with a second carrier the global service discoveryserver identifies a host server of the second carrier and the mobiledevice is updated to be associated with the second carrier. Usually theglobal service discovery server identifies an operator and country ofuse.

Often the global service discovery server checks whether the mobiledevice is registered. If the mobile device is registered the globalservice discovery server updates the mobile device profile but if notregistered the global service discovery server registers the mobiledevice. Often the mobile device profile includes at least one of an IMEInumber, a device manufacturer, a carrier, and a country of use.

The stub maybe activated upon receiving a Short Messaging Service (SMS)from the operating server. That server may be identified by the globalservice discovery server.

In practice the stub may requests application software from theoperating server. If so, the operating server may send the mobile devicerequested application software.

The stub itself may be embedded by an original equipment manufacturer.The global service discovery server may send the mobile device a mobilecountry code (MCC), a mobile network code (MNC), and an Internationalmobile station equipment identity (IMEI).

According to yet another aspect of the invention, the invention is anetwork comprising a mobile device having a mobile device processor,mobile device transient memory, a SIM card, a mobile device profile,mobile device non-transitory memory, mobile device bi-directionalcommunication capabilities, a mobile device operating system embedded inthe mobile device non-transitory memory, and a configurable stub havinga stub configuration embedded in the mobile device non-transitorymemory. The network may further includes a processor controlledoperating server having an operating server processor, operating servernon-transitory memory, operating server bi-directional communicationcapabilities, an operating server operating system embedded in theoperating server non-transitory memory, wherein the operating server isconfigured to support traffic management protocols and to support thebi-directional communications of the mobile device subject to thetraffic management protocols, and wherein the operating server isconfigured to send Short Messaging Service (SMS) messages. That networkmay also include a processor controlled global service discovery serverconfigured to receive the stub configuration and to inform the mobiledevice about the operating server. The stub sends the global servicediscovery server a request to register the mobile device. In responsethe global service discovery server registers the mobile device. Afterthe operating server sends activation SMS to the mobile device the stubcauses the mobile device to request an operation configuration from theoperating server which the operating server sends to the mobile device.

In practice the stub causes the mobile device to communicate with theglobal service discovery server when the mobile device initially bootsup, when the mobile device resets, or when a SIM card is changed. If themobile device is associated with a first carrier but the changed SIMcard is associated with a second carrier the global service discoveryserver identifies a host server of the second carrier and the mobiledevice is updated to be associated with the second carrier.

According to another aspect of the invention that invention takes theform of a mobile device having a processor, transient memory, a SIMcard, non-transitory memory storing an operating system; andcommunication hardware to provide bi-directional communications. Thenon-transitory memory further stores a mobile device profile and a stub.The stub directs the processor to cause the communication hardware tocontact a global service discovery server to obtain information about anoperating server configured to support bi-directional communications ofmobile device.

In practice, the stub directs the processor to cause the communicationhardware to contact the global service discovery server when the mobiledevice initially boots up, when the mobile device resets, or when a SIMcard is changed.

According to still another aspect of the invention that invention takesthe form of a mobile device having a processor, transient memoryoperatively connected to the processor, a SIM card operatively connectedto the processor, non-transitory memory operatively connected to theprocessor and storing an operating system; and communication hardwareoperatively connected to the processor to provide bi-directionalcommunications in accord with traffic management protocols. Thenon-transitory memory also stores a mobile device profile and a stub.The stub directs the processor to cause the communication hardware tocontact a global service discovery server to register the mobile deviceand to obtain information about an operating server that is configuredto support bi-directional communications in accord with the trafficmanagement protocols. When the mobile device receives an activation SMSfrom the operating server the mobile device request an operationconfiguration from the operating server. The mobile device stores thereceived operation configuration in the mobile device profile.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 is a system diagram according to one or more embodimentsdisclosed herein;

FIG. 2 is a signal flow diagram according to one or more embodimentsdisclosed herein;

FIG. 3 is a diagram of various operating servers according to one ormore embodiments disclosed herein;

FIG. 4 is a user interface display as a tool provided in communicationwith an operating server or global server according to one or moreembodiments disclosed herein; and

FIG. 5 is a user interface display as a tool provided in communicationwith an operating server or global server according to one or moreembodiments disclosed herein.

DETAILED DESCRIPTION

The following description and drawings are illustrative and are not tobe construed as limiting. Numerous specific details are described toprovide a thorough understanding of the disclosure. However, in certaininstances, well-known or conventional details are not described in orderto avoid obscuring the description. References to one or an embodimentin the present disclosure can be, but not necessarily are, references tothe same embodiment; and, such references mean at least one of theembodiments.

Reference in this specification to “one embodiment” or “an embodiment”means that a particular feature, structure, or characteristic describedin connection with the embodiment is included in at least one embodimentof the disclosure. The appearances of the phrase “in one embodiment” invarious places in the specification are not necessarily all referring tothe same embodiment, nor are separate or alternative embodimentsmutually exclusive of other embodiments. Moreover, various features aredescribed which may be exhibited by some embodiments and not by others.Similarly, various requirements are described which may be requirementsfor some embodiments but not other embodiments.

The terms used in this specification generally have their ordinarymeanings in the art, within the context of the disclosure, and in thespecific context where each term is used. Certain terms that are used todescribe the disclosure are discussed below, or elsewhere in thespecification, to provide additional guidance to the practitionerregarding the description of the disclosure. For convenience, certainterms may be highlighted, for example using italics and/or quotationmarks. The use of highlighting has no influence on the scope and meaningof a term; the scope and meaning of a term is the same, in the samecontext, whether or not it is highlighted. It will be appreciated thatsame thing can be said in more than one way.

Consequently, alternative language and synonyms may be used for any oneor more of the terms discussed herein, nor is any special significanceto be placed upon whether or not a term is elaborated or discussedherein. Synonyms for certain terms are provided. A recital of one ormore synonyms does not exclude the use of other synonyms. The use ofexamples anywhere in this specification including examples of any termsdiscussed herein is illustrative only, and is not intended to furtherlimit the scope and meaning of the disclosure or of any exemplifiedterm. Likewise, the disclosure is not limited to various embodimentsgiven in this specification.

Without intent to limit the scope of the disclosure, examples ofinstruments, apparatus, methods and their related results according tothe embodiments of the present disclosure are given below. Note thattitles or subtitles may be used in the examples for convenience of areader, which in no way should limit the scope of the disclosure. Unlessotherwise defined, all technical and scientific terms used herein havethe same meaning as commonly understood by one of ordinary skill in theart to which this disclosure pertains. In the case of conflict, thepresent document, including definitions will control.

Embodiments of the present disclosure include systems and methods forsecure mechanism to deliver mobile traffic management configuration uponstub configuration on a mobile device by a global service discoveryserver. The disclosed innovation includes the example components: thestub and the GSD (global service discovery) server. The former can bedistributed through the original equipment manufacturer (OEM)integration and the latter can be hosted by the host server. In oneembodiment, the OEM can host their specific instance. Note that inembodiments of the present disclosure, the host server and local proxyare components of the present innovation which individually and incombination provide mobile device resource, mobile network and/or mobiletraffic resource management, optimization functionalities and features.

The stub and the GSD (global service discovery) server can be used for,for example: discovering the host server when stubs get activated withSMS messages; or, registering devices (the server can store storingmobile country code (MCC)+mobile network code (MNC)+International mobilestation equipment identity (IMEI)).

Embodiments of the present disclosure include systems and methods forsecure mechanism to deliver mobile traffic management configuration uponstub configuration on a mobile device by a global service discoveryserver. The disclosed innovation includes the example components: thestub and the GSD (global service discovery server) server. The formercan be distributed through the original equipment manufacturer (OEM)integration and the latter can be hosted by the host server. Note thatin embodiments of the present disclosure, the host server and localproxy are components of the present innovation which individually and incombination provide mobile device resource, mobile network and/or mobiletraffic resource management, optimization functionalities and features.

As illustrated in FIG. 1, a system 100 is depicted. The system 100includes a mobile device 110. The mobile device 110 may be a personaldisplay device, a cellular phone, a smart-phone, and the like. Themobile device 110 may further include an International Mobile StationEquipment Identify number (IMEI) that is used for identifying the mobiledevice. IMEI or its hash may be used for identifying the mobile device.A SIM card 114 may be provided with the mobile device 110 and may benetwork or carrier specific. A stub 116, as further described herein,may also be embodied on the mobile device 110. Memory 118 and aprocessor 119 may also be provided.

A global server 120 may be provided. An operating server 130 may be incommunication with the mobile device 110 and be operating over acellular network. The operating server 130 may be carrier specific inone or more embodiments.

A signal flow diagram representing one or more methods disclosed hereinis illustrated in FIG. 2. The stub 116 may be configured to requestregistration from the global server 120, and, in response to thatrequest, the global server 120 may be configured to send a deviceregistration response to stub 116. During this period, the mobile device110 may be inactive until the operator server 130 communicates via anactivation SMS to the stub 116. The stub 116 may then request operationconfiguration instructions or programs from the global server 120, and,in response thereto, the global server 120 may send operationconfiguration instructions which are received by stub 116. The stub 116may request application software from the operator server 130, and, inresponse thereto, the operator server 130 may communicate applicationsoftware to stub 116, which receives the application software. The stub116 or mobile device 110 may then verify an upgrade application andinstall the upgrade application software.

The stub 116 and the GSD 120 can be used for, for example: discoveringthe host server when stubs get activated with SMS messages. In one ormore embodiments, the stub 116 and global server 120 may be used forregistering devices (the server 120 can store storing mobile countrycode (MCC)+mobile network code (MNC)+International mobile stationequipment identity (IMEI) or its hashed form).

In one embodiment, the stub 116 can be configured to operate in multiplemodes (e.g., two modes). For example, in one mode, stub 116 may beconfigured for a silent mode. In this mode, the stub 116 or mobiledevice 110 runs upon receiving an activation SMS or other messages ortriggers. The SMS or other message or trigger may be received from theglobal server 120 or the operator server 130.

In another mode, stub 116 may be configured for operating in a“registering mode.” In this mode, the stub 116 contacts the GSD server120 when the mobile device 110 boots for the first time, after themobile device 110 resets, and/or when SIM card 114 is changed, or whenthe SIM card 114 performs periodic sync ups. The information obtainedduring registrations can be used to find or activate phones or mobiledevices 110 that have been sold before the operator installs the hostserver (e.g., the proxy server, or functionalities provided by the proxyserver) or mobile devices that are not subsidized by operator (not underoperator's control).

In the silent mode, the stub 116 can be activated with an SMS message orother types of messages or triggers. Then the stub 116 communicates withthe goes to GSD 120 (global service discovery server) and determines oridentifies the operator and country specific configuration for theparticular host server for the geographic region (e.g., country,location, region, etc.) and determines, identifies, and/or retrieves theassociated local proxy client package from there. In one or moreembodiments, stub 116 may identify a lesser number of thesecharacteristics. In the registration mode, the stub 116 registers withthe GSD 120 (global service discovery server). Activation occursaccording to the description already provided herein. When mobiledevices 110 move between networks, such as when SIM cards are changed,the stub 116 can verify with GSD 120 to determine whether there is ahost server available (for the network of the new SIM card).

If there is a host server available for the network (e.g., the networkservice provider or the carrier has integrated the host server'sservices, platform, or server), the stub 116 will obtain the newconfiguration applicable to the new network and upgrade itself, but ondifferent mobile network. In this manner, the activation can happenautomatically and on the fly (no SMS may be required). In oneembodiment, this can be configured and reconfigured (turned on or off)based on operator's wishes.

In one or more embodiments, on a mobile device 110, a local proxy/stub116 can discover if an operator that is supplying the present SIM card114 has an instance of a host server and/or where it is locatedgeographically. In one or more embodiments, if a carrier/mobile operatorinstalls or integrates a host server (e.g., proxy server orfunctionalities/on its network or network server), there are mobiledevices with stubs that can start using the host server and/or itsfunctionalities right away. The operator needs to be able to find outthe list for potential remote activation.

The following functionalities (minimal functional requirement) areassumed to be provided globally by the service:

The stub is inactive until activated by an SMS message. In oneembodiment, stubs 116 can connect to service and/or the GSD (globalservice discovery server) to check for configuration, which can provideinformation about the operator and/or country of the active SIM card andthe device.

Service will check if the operator/country/device combination or itspart has been registered before. If no, the combination will beregistered. If yes, the device's profile will be updated. Based onMCC/MNC combination the service can determine if there is a host serverconfiguration available and return it in case of success or returnnothing if there is no host server available.

FIGS. 4 and 5 show example operator user interfaces. Each operator canhave its own page or view based on credentials provided by the system.For example, as illustrated in FIG. 4, an operator can view and filterdevices by OEM or device vendor, model, operating system, version,region, and the like and can further limit timeline of when devicesregistered. For example, an operator can select a date range to viewsresults corresponding to the selected data range. The user interface canalso include an export feature that allows an operator to save or exportthe result list as a CSV, XLS, RTF, and any other suitable format.

When the configuration tab is selected from the user interface shown inFIG. 4, the user interface of FIG. 5 is displayed. Via the configurationpage, an operator can turn on/off automatic activation of new devicesthat appear in the operator's network after a host server is availableor discovered. When a new device checks for configuration on, forexample, SIM swap (i.e., replacing existing SIM with a new SIM), aconfiguration for the host server can be returned right away, so thereis no need to activate the device separately by an SMS message. The userinterface can also include a subscription feature that allows anoperator to subscribe for notification once a configurable number (e.g.,1000, 500) of devices have been registered or activated. Theconfigurations are then saved by the system.

One embodiment of the present innovation includes an administrativeinterface which can be used for, for example: debug, configuration anddata querying purposes. In addition to standard maintenance scenarios itcan also be used to query for devices on specific operator's networkthat can be upgraded or configured to work with the host server.

An example architecture of the disclosed technology is shown in FIG. 3.There can be multiple instances of the data center geographicallydistributed in the disclosed innovation, for example in EU/Ireland andUS/Oregon. The data centers may be operating servers 130A and 130B.However, more can be transparently provisioned later based on the numberof devices spread over different geographical locations/continents.

Each data center can include, for example, an ELB (elastic loadbalancer) on entrance balancing (round robin) requests acrossapplication servers. Application servers can be placed into more thanone availability zone. Therefore, fail over is supported on twolevels—inside a single data center as well as between data centers. EachELB is configured to make sure that 1) at least two application serverinstances are available per DC, 2) instances are located in differentavailability zones. When an instance of a data center misbehaves,breaks, or disappears ELB (elastic load balancer) can spawn another onemaking sure two application servers instance are running as minimum.

The distributed database (e.g., SimpleDB) can be used as a storage foroperator specific configurations as well as for storing device profiles.High-availability and cross data center replication is provided as apart of managed service. The distributed database (e.g., SimpleDB) caninclude a key/value store that does basic indexing that allows lookupsin values.

Every service instance can perform daily backups or archiving (e.g., orat other timing intervals). Service instances can spread times ofbackups over 24 hours to minimize potential risk window. For example,for two-instance system: one instance would make backups at 12 a.m. andthe other at 12 p.m., 8 hours shift would be used for three instances,and so on.

Due to auto scaling used, application server instances can come and goautomatically. To keep track record of events, syslog-ng can be used tohave a centralized copy of log files in each data center. Auto scalingcan be implemented as a policy that is provisioned to a networkmonitoring service. The service may spawn an application server eachtime a scale out rule is triggered. It will also shut down an app servereach time a scale down criterion is satisfied. The general rule is:scale out/up aggressively, scale down carefully. The average CPUutilization is used as a trigger:

In one embodiment, every time the average (for app servers) CPUutilization reaches 60% over five minutes interval a new applicationserver instance can be added

In one embodiment, every time the average CPU utilization drops below athreshold, for example over a certain amount of time, for example, 30%or less over a five minute interval, a random application serverinstance can be shut down.

The disclosed technique provides a secure way to deliver configurationupon activation. Since the stub itself is in one embodiment, generic. Inintegration with OEMs we may not know where the mobile devices are goingto end up after being sold (country, operator, etc.) The information isnot ideally provided in an SMS' body since SMS can be faked (spoofed).Therefore, when the stub is activated communicates with the GSD toobtain information about the host server instance for this particularoperator.

The disclosed technology enables mobile devices moving from one operatorto another (and between countries). None, or both, or any of operatorsmay have one or more of the host server(s).

When one or more host servers are installed in an operator's network,the stubs allow the operator to “find” phones on already on theirnetwork that have stubs and can be activated. The disclosed technologycan be used to approach operators saying that there are already ‘N’mobile devices that are network management capable, in other words,enabled to utilize the traffic management and/or device resourcemanagement services provided by the host server and/or the local proxyclient. Note that in embodiments of the present disclosure, the hostserver and local proxy are components of the present innovation whichindividually and in combination provide mobile device resource, mobilenetwork and/or mobile traffic resource management, optimizationfunctionalities and features. In a further embodiment, the disclosedtechnology also handles with situations when mobile devices are reset.When a mobile device is reset, the local proxy is removed and theoriginal stub is restored. Since the stub is configured and implementedto automatically communicate with the GSD (global service discoveryserver) to check for configuration, after mobile devices reset, theywill retrieve or obtain the configuration and install the local proxyagain.

A further embodiment of the disclosed technology includes security andprotection of the local proxy package. When the GSD is provisioned witha new operator specific configuration for traffic and network resourcemanagement provided by the host server instance (s), which has a“secret” (key) as a part of it. Same key can be tracked, managed, andretained by the host server instance. For example, when a mobile deviceis activated it comes to the GSD (global service discovery server) andobtains a device specific token as a part of the returned configuration.This token can be sent to the host server when the stub attempts todownload the local proxy client package. Having the same key, the hostserver can verify the validity of the token and return and send thelocal proxy client package upon determining that the token is valid

In general, the routines executed to implement the embodiments of thedisclosure, may be implemented as part of an operating system or aspecific application, component, program, object, module or sequence ofinstructions referred to as “computer programs.” The computer programstypically comprise one or more instructions set at various times invarious memory and storage devices in a computer, and that, when readand executed by one or more processing units or processors in acomputer, cause the computer to perform operations to execute elementsinvolving the various aspects of the disclosure.

Moreover, while embodiments have been described in the context of fullyfunctioning computers and computer systems, those skilled in the artwill appreciate that the various embodiments are capable of beingdistributed as a program product in a variety of forms, and that thedisclosure applies equally regardless of the particular type of machineor computer-readable media used to actually effect the distribution.

Further examples of machine-readable storage media, machine-readablemedia, or computer-readable (storage) media include, but are not limitedto, recordable type media such as volatile and non-volatile memorydevices, floppy and other removable disks, hard disk drives, opticaldisks (e.g., Compact Disk Read-Only Memory (CD ROMS), Digital VersatileDisks, (DVDs), etc.), among others, and transmission type media such asdigital and analog communication links.

Unless the context clearly requires otherwise, throughout thedescription and the claims, the words “comprise,” “comprising,” and thelike are to be construed in an inclusive sense, as opposed to anexclusive or exhaustive sense; that is to say, in the sense of“including, but not limited to.” As used herein, the terms “connected,”“coupled,” or any variant thereof, means any connection or coupling,either direct or indirect, between two or more elements; the coupling ofconnection between the elements can be physical, logical, or acombination thereof. Additionally, the words “herein,” “above,” “below,”and words of similar import, when used in this application, shall referto this application as a whole and not to any particular portions ofthis application. Where the context permits, words in the above DetailedDescription using the singular or plural number may also include theplural or singular number respectively. The word “or,” in reference to alist of two or more items, covers all of the following interpretationsof the word: any of the items in the list, all of the items in the list,and any combination of the items in the list.

The above detailed description of embodiments of the disclosure is notintended to be exhaustive or to limit the teachings to the precise formdisclosed above. While specific embodiments of, and examples for, thedisclosure are described above for illustrative purposes, variousequivalent modifications are possible within the scope of thedisclosure, as those skilled in the relevant art will recognize. Forexample, while processes or blocks are presented in a given order,alternative embodiments may perform routines having steps, or employsystems having blocks, in a different order, and some processes orblocks may be deleted, moved, added, subdivided, combined, and/ormodified to provide alternative or subcombinations. Each of theseprocesses or blocks may be implemented in a variety of different ways.Also, while processes or blocks are at times shown as being performed inseries, these processes or blocks may instead be performed in parallel,or may be performed at different times. Further, any specific numbersnoted herein are only examples: alternative implementations may employdiffering values or ranges.

The teachings of the disclosure provided herein can be applied to othersystems, not necessarily the system described above. The elements andacts of the various embodiments described above can be combined toprovide further embodiments. Aspects of the disclosure can be modified,if necessary, to employ the systems, functions, and concepts of thevarious references described above to provide yet further embodiments ofthe disclosure.

These and other changes can be made to the disclosure in light of theabove Detailed Description. While the above description describescertain embodiments of the disclosure, and describes the best modecontemplated, no matter how detailed the above appears in text, theteachings can be practiced in many ways. As noted above, particularterminology used when describing certain features or aspects of thedisclosure should not be taken to imply that the terminology is beingredefined herein to be restricted to any specific characteristics,features, or aspects of the disclosure with which that terminology isassociated. In general, the terms used in the following claims shouldnot be construed to limit the disclosure to the specific embodimentsdisclosed in the specification, unless the above Detailed Descriptionsection explicitly defines such terms. Accordingly, the actual scope ofthe disclosure encompasses not only the disclosed embodiments, but alsoall equivalent ways of practicing or implementing the disclosure underthe claims.

1. A network, comprising: a mobile device having a mobile deviceprocessor, mobile device transient memory, a SIM card, mobile devicenon-transitory memory storing a mobile device profile, mobile devicebi-directional communication capabilities, a mobile device operatingsystem embedded in the mobile device non-transitory memory, and aconfigurable stub having a stub configuration embedded in the mobiledevice non-transitory memory; an operating server having an operatingserver processor, operating server non-transitory memory, operatingserver bi-directional communication capabilities, an operating serveroperating system stored in the operating server non-transitory memory,wherein the operating server is configured to support traffic managementprotocols that support the bi-directional communications of the mobiledevice subject, and wherein the operating server is configured to sendShort Messaging Service (SMS) messages; and a processor controlledglobal service discovery server configured to receive the stubconfiguration and to inform the mobile device about the operatingserver.
 2. The network of claim 1, wherein the stub causes the mobiledevice to communicate with the global service discovery server when themobile device initially boots up.
 3. The network of claim 1, wherein thestub causes the mobile device to communicate with the global servicediscovery server when the mobile device resets.
 4. The network of claim1, wherein the stub causes the mobile device to communicate with theglobal service discovery server when the SIM card is changed.
 5. Thenetwork of claim 4, wherein when the mobile device is associated with afirst carrier but the changed SIM card is associated with a secondcarrier the global service discovery server identifies a host server ofthe second carrier and the mobile device is updated to be associatedwith the second carrier.
 6. The network of claim 1, wherein the globalservice discovery server identifies an operator and country of use. 7.The network of claim 1, wherein the global service discovery serverchecks whether the mobile device is registered.
 8. The network of claim7, wherein, if the mobile device is registered the global servicediscovery server updates the mobile device profile.
 9. The network ofclaim 7, wherein the global service discovery server registers themobile device it the mobile device is not registered.
 10. The network ofclaim 7, wherein the mobile device profile includes at least one of anIMEI number, a hashed IMEI number, a device manufacturer, a carrier, anda country of use.
 11. The network of claim 1, wherein the stub isactivated upon receiving a Short Messaging Service (SMS) from theoperating server.
 12. The network of claim 11, wherein global servicediscovery server identifies the operating server.
 13. The network ofclaim 12, wherein the stub requests application software from theoperating server.
 14. The network of claim 13, wherein the operatingserver sends the mobile device application software.
 15. The network ofclaim 1, wherein the stub is embedded by an original equipmentmanufacturer.
 16. The network of claim 1, wherein the global servicediscovery server sends the mobile device a mobile country code (MCC), amobile network code (MNC), and information required to obtain anInternational mobile station equipment identity (IMEI).
 17. The networkof claim 1, wherein the global service discovery server stores a key,the operator server stores the same key, the global service discoveryserver sends the key to the mobile device, the mobile device sends thatkey to the operator server, and the operator server verifies thevalidity of the key and sends the mobile device application software ifthe key if valid.
 18. A network, comprising: a mobile device having amobile device processor, mobile device transient memory, a SIM card, amobile device profile, mobile device non-transitory memory, mobiledevice bi-directional communication capabilities, a mobile deviceoperating system embedded in the mobile device non-transitory memory,and a configurable stub having a stub configuration embedded in themobile device non-transitory memory; a processor controlled operatingserver having an operating server processor, operating servernon-transitory memory, operating server bi-directional communicationcapabilities, an operating server operating system embedded in theoperating server non-transitory memory, wherein the operating server isconfigured to support traffic management protocols and to support thebi-directional communications of the mobile device subject to thetraffic management protocols, and wherein the operating server isconfigured to send Short Messaging Service (SMS) messages; and aprocessor controlled global service discovery server configured toreceive the stub configuration and to inform the mobile device about theoperating server; wherein the stub sends the global service discoveryserver a request to register the mobile device; wherein the globalservice discovery server registers the mobile device; wherein theoperating server sends an activation SMS to the mobile device; whereinin response to the SMS the stub causes the mobile device to request anoperation configuration; and wherein operating server sends theoperation configuration to the mobile device.
 19. The network of claim18, wherein the stub causes the mobile device to request applicationsoftware from the operating server.
 20. The network of claim 19, whereinthe operating server sends the requested application software to themobile device.
 21. The network of claim 20, wherein the mobile deviceinstalls the application software.
 22. The network of claim 18, whereinthe stub causes the mobile device to communicate with the global servicediscovery server when the mobile device initially boots up.
 23. Thenetwork of claim 18, wherein the stub causes the mobile device tocommunicate with the global service discovery server when the mobiledevice resets.
 24. The network of claim 18, wherein the stub causes themobile device to communicate with the global service discovery serverwhen a SIM card is changed.
 25. The network of claim 24, wherein themobile device is associated with a first carrier but the changed SIMcard is associated with a second carrier the global service discoveryserver identifies a host server of the second carrier and the mobiledevice is updated to be associated with the second carrier.
 26. Thenetwork of claim 18, wherein the global service discovery serveridentifies an operator and country of use.
 27. The network of claim 18,wherein the operation configuration includes at least one of an IMEInumber, a hashed IMEI number, a device manufacturer, a carrier, and acountry of use.
 28. The network of claim 18, wherein the stub isembedded by an original equipment manufacturer.
 29. The network of claim18, wherein the operating server sends the mobile device a mobilecountry code (MCC), a mobile network code (MNC), and information toobtain an International mobile station equipment identity (IMEI). 30.The network of claim 18, wherein the global service discovery serverstores a key, the operator server stores that key, the global servicediscovery server sends the key to the mobile device, the mobile devicesends that key to the operator server, and the operator server verifiesthe validity of the key and sends the mobile device application softwareif the key if valid.
 31. A mobile device, having: a processor; transientmemory operatively connected to said processor; a SIM card operativelyconnected to said processor; non-transitory memory operatively connectedto said processor and storing an operating system; and communicationhardware operatively connected to said processor to providebi-directional communications in accord with traffic managementprotocols; wherein the non-transitory memory further stores a mobiledevice profile and a stub; wherein the stub directs the processor tocause the communication hardware to contact a global service discoveryserver to register the mobile device and to obtain information about anoperating server that is configured to support bi-directionalcommunications in accord with the traffic management protocols; whereinthe mobile device received an activation SMS from the operating server;wherein the mobile device request an operation configuration from theoperating server; and wherein the mobile device stored a receivedoperation configuration in the mobile device profile.